Methods and apparatus to prevent potential conflicts among instances of son functions

ABSTRACT

Methods are provided to prevent a potential conflict among first and second instances of SON functions. A first input impact time, first input scope and first objective of the first instance, and a second input impact time, second input scope and second objective of the second instance are obtained. If there is a first overlap among the first input impact time and the second input impact time, whether there is a second overlap among the first input scope and the second input scope is determined. If there is the second overlap, whether the first objective and the second objective are the same or substantially the same is determined. If so, it is determined that the potential conflict exists. If there is the second overlap, whether the first objective contradicts or substantially contradicts with the second objective is determined. If so, it is determined that the potential conflict exists.

TECHNICAL FIELD

Example embodiments disclosed herein relate to communication networks,particularly, to self-organizing networks.

BACKGROUND

The evolvement of communication technology, especially the wirelesscommunication technology, has increased the complexity of networks andthe amount of network nodes, thereby increasing operation andmaintenance tasks i.e. management tasks. To automate at least some ofthe tasks a concept called a self-organizing network (SON) is introducedby Next Generation Mobile Networks (NGMN) Alliance and 3GPP (ThirdGeneration Partnership Project) to be used first in long term evolution(LTE) access networks, and later on in other networks, both in accessand core networks. A self-organizing network is capable toself-configure and continuously self-optimize itself in response tonetwork and traffic changes. In such a network, the network and/or anetwork node alters automatically, preferably without human involvement,its configuration parameters, such as transmission and/or receptionparameters, by means of different self-organizing network functions.Since monitored network behavior triggers execution of one or moreself-organizing function instances, it may happen that severalindependent self-organizing function instances are active concurrentlyin the same network area with different targets. Thus, it would beuseful to coordinate the self-organizing network functions. Onechallenge for the coordination is that “plug and play” network elementsthat support self-organizing network functionality can be bought fromany vendor, and instead of buying single network elements, acommunication service provider may buy vendor-specific domains, and/ororganize network elements bought from different vendors to differentvendor-specific domains, each covering a geographical area and notknowing the run-time situation of other domains.

BRIEF DESCRIPTION OF THE DRAWINGS

Example embodiments disclosed throughout the Detailed Description willbe described in greater detail with reference to accompanying drawings,in which:

FIG. 1 is a block diagram illustrating a communication system, accordingto an example embodiment;

FIG. 2 is a block diagram illustrating a communication system, accordingto an example embodiment;

FIG. 3 is a flow chart illustrating a method to prevent a potentialconflict among a first instance of a self-organizing network (SON)function and a second instance of a SON function, according to anexample embodiment;

FIG. 4 is a flow chart illustrating a method to prevent a potentialconflict among a first instance of a SON function and a second instanceof a SON function, according to an example embodiment;

FIG. 5 is a flow chart illustrating a method to prevent a potentialconflict among a first instance of a SON function and a second instanceof a SON function, according to an example embodiment;

FIG. 6 is a flow chart illustrating a method to prevent a potentialconflict among a first instance of a SON function and a second instanceof a SON function, according to an example embodiment; and

FIG. 7 is a flow chart illustrating a method to prevent a potentialconflict among a first instance of a SON function and a second instanceof a SON function, according to an example embodiment.

DETAILED DESCRIPTION

The embodiments disclosed throughout this Detailed Description areexamples. Although this Detailed Description may refer to “an”, “one”,or “some” example embodiment(s) in several locations, this does notnecessarily mean that each such reference is to the same exampleembodiment(s), or that the feature only applies to a single exampleembodiment. Single features of different example embodiments may also becombined to provide other example embodiments.

The example embodiments disclosed throughout this Detailed Descriptionare applicable to any communication system or any combination ofdifferent communication systems and corresponding networks and networkelements (including “plug and play” network elements”) that supportself-organizing network functionality. The communication system may be awireless communication system or a communication system utilizing bothfixed networks and wireless networks or a fixed communication system.Furthermore, the communication system may be used in any radio accessnetwork, core network and any self-organizing network (SON). Thespecifications of communication systems and networks, especially inwireless communication, develop rapidly. Such development may requireextra changes to an example embodiment. Therefore, all words andexpressions should be interpreted broadly and they are intended toillustrate, not to restrict, the example embodiments.

FIG. 1 illustrates communication system 100, that includes a SONfunction manager 130 that is configured to manage SON functions for aparticular domain (referred to in FIG. 1 and in the discussion of FIG. 1as Domain A), and two network elements 150 and 170 of Domain A. Asdiscussed throughout this Detailed Description, a domain can be definedas a designated section of a radio access network. In exampleembodiments, the section can be designated by the network elementslocated in a particular geographical area and/or the network elementsthat are managed by a particular vendor.

In an example embodiment, Domain A SON function manager 130 is acomputing device including a processor 132 configured to execute SONfunction manager software application 136 for Domain A. Processor 132 iscommunicatively connected to and interacts directly or indirectly withmemory 134 and communication subsystem 138. Memory 134 stores SONfunction manager software application 136 for Domain A (which includes adatabase 140, SON functions 142 for Domain A, and methods 300-700 (ofFIGS. 3-7, but not shown in FIG. 1) for preventing potential conflictsamong SON functions). Communication subsystem 138 sends and receivescommunications (such as for example requests to execute a SON functioninstance, requests to output at least one information element by a SONfunction instance, responses to the requests, and information about SONfunction instances) to and from processor 132.

Regarding the SON functions discussed throughout this DetailedDescription, in example embodiments, a number of different SON functionscould be used for automatically performing management actions, such asfault, configuration, accounting, performance and security management.Examples of SON functions include mobility load balancing, handoveroptimization, coverage and capacity optimization, cell outagemanagement, and mobility robustness optimization.

In an example embodiment, Domain A Network Element 1 150 is a computingdevice including a processor 152 configured to execute SON functioninstances 162 for Network Element 1 that is within Domain A. Processor152 is communicatively connected to and interacts directly or indirectlywith memory 154 and communication subsystem 158. Memory 154 storesNetwork Element 1 SON functions 162. Communication subsystem 158 sendsand receives communications (such as for example requests to execute aSON function instance, requests to output at least one informationelement by a SON function instance, responses to the requests, andinformation about SON function instances) to and from processor 152.

In an example embodiment, Domain A Network Element 2 170 is a computingdevice including a processor 172 configured to execute instances of SONfunctions 182 for Network Element 2 that is within Domain A. Processor172 is communicatively connected to and interacts directly or indirectlywith memory 174 and communication subsystem 178. Memory 174 storesNetwork Element 2 SON functions 182. Communication subsystem 178 sendsand receives communications (such as for example requests to execute aSON function instance, requests to output at least one informationelement by a SON function instance, responses to the requests, andinformation about SON function instances) to and from processor 172.

Communication subsystem 138 (of Domain A SON function manager 130) iscommunicatively connected to and interacts directly or indirectly withcommunication subsystem 158 (of Domain A Network Element 1150) usinginterface 110. Accordingly, it is through communication subsystems 138and 158 and interface 110, that processor 152 is communicativelyconnected to and interacts directly or indirectly with processor 132 andDomain A database 140.

Communication subsystem 138 also is communicatively connected to andinteracts directly or indirectly with communication subsystem 178 (ofDomain A Network Element 2 170) using interface 120. Accordingly, it isthrough communication subsystems 138 and 178 and interface 120, thatprocessor 172 is communicatively connected to and interacts directly orindirectly with processor 132 and Domain A database 140.

Communication subsystem 158 is communicatively connected to andinteracts directly or indirectly with communication subsystem 178 usinginterface 190. Accordingly, it is through communication subsystems 158and 178 and interface 120, that processor 152 is communicativelyconnected to and interacts directly or indirectly with processor 172.

FIG. 2 illustrates communication system 200, that includes: a networkSON function manager 210 configured to manage SON functions for twodomains (referred to in FIG. 2 and the discussion of FIG. 2 as Domains Aand B); SON function manager 230 a configured to manage SON functionsfor Domain A; SON function manager 230 b configured to manage SONfunctions for Domain B; network element 250 a of Domain A; and networkelement 250 b of Domain B.

In an example embodiment, network SON function manager 210 is acomputing device including a processor 212 configured to execute SONfunction manager software application 216 for Domains A and B. Processor212 is communicatively connected to and interacts directly or indirectlywith memory 214 and communication subsystem 218. Memory 214 stores SONfunction manager software application 216 for Domains A and B (whichincludes a database 220, SON functions 222 for Domains A and B, andmethods 300-700 (of FIGS. 3-7, but not shown in FIG. 2) for preventingpotential conflicts among SON functions). Communication subsystem 218sends and receives communications (such as for example requests toexecute a SON function instance, requests to output at least oneinformation element by a SON function instance, responses to therequests, and information about SON function instances) to and fromprocessor 212.

In an example embodiment, Domain A SON function manager 230 a is acomputing device including a processor 232 a configured to execute SONfunction manager software application 236 a for Domain A. Processor 232a is communicatively connected to and interacts directly or indirectlywith memory 234 a and communication subsystem 238 a. Memory 234 a storesSON function manager software application 236 a for Domain A (whichincludes a database 240 a, SON functions 242 a for Domain A, and methods300-700 (of FIGS. 3-7, but not shown in FIG. 2) for preventing potentialconflicts among SON functions). Communication subsystem 238 a sends andreceives communications (such as for example requests to execute a SONfunction instance, requests to output at least one information elementby a SON function instance, responses to the requests, and informationabout SON function instances) to and from processor 232 a.

In an example embodiment, Domain B SON function manager 230 b is acomputing device including a processor 232 b configured to execute SONfunction manager software application 236 b for Domain B. Processor 232b is communicatively connected to and interacts directly or indirectlywith memory 234 b and communication subsystem 238 b. Memory 234 b storesSON function manager software application 236 b for Domain B (whichincludes a database 240 b, SON functions 242 b for Domain B, and methods300-700 (of FIGS. 3-7, but not shown in FIG. 2) for preventing potentialconflicts among SON functions). Communication subsystem 238 b sends andreceives communications (such as for example requests to execute a SONfunction instance, requests to output at least one information elementby a SON function instance, responses to the requests, and informationabout SON function instances) to and from processor 232 b.

In an example embodiment, Domain A Network Element 250 a is a computingdevice including a processor 252 a configured to execute instances ofSON functions 262 a for network element 250 a that is within Domain A.Processor 252 a is communicatively connected to and interacts directlyor indirectly with memory 254 a and communication subsystem 258 a.Memory 254 a stores SON functions 262 a for Domain A Network Element 250a. Communication subsystem 258 a sends and receives communications (suchas for example requests to execute a SON function instance, requests tooutput at least one information element by a SON function instance,responses to the requests, and information about SON functions) to andfrom processor 252 a.

In an example embodiment, Domain B Network Element 250 b is a computingdevice including a processor 252 b configured to execute instances ofSON functions 262 b for network element 250 b that is within Domain B.Processor 252 b is communicatively connected to and interacts directlyor indirectly with memory 254 b and communication subsystem 258 b.Memory 254 b stores SON functions 262 b for Domain B Network Element 250b. Communication subsystem 258 b sends and receives communications (suchas for example requests to execute a SON function instance, requests tooutput at least one information element by a SON function instance,responses to the requests, and information about SON function instances)to and from processor 252 b.

Communication subsystem 218 (of Network SON function manager 210) iscommunicatively connected to and interacts directly or indirectly withcommunication subsystem 238 a (of Domain A SON function manager 230 a)using interface 260 a. Accordingly, it is through communicationsubsystems 218 and 238 a and interface 260 a, that processor 232 a iscommunicatively connected to and interacts directly or indirectly withprocessor 212 and Network database 220.

Communication subsystem 218 also is communicatively connected to andinteracts directly or indirectly with communication subsystem 238 b (ofDomain B SON function manager 230 b) using interface 260 b. Accordingly,it is through communication subsystems 218 and 238 b and interface 260b, that processor 232 b is communicatively connected to and interactsdirectly or indirectly with processor 212 and Network database 220.

Communication subsystem 238 a is communicatively connected to andinteracts directly or indirectly with communication subsystem 238 busing interface 264. Accordingly, it is through communication subsystems238 a and 238 b and interface 264, that processor 232 a iscommunicatively connected to and interacts directly or indirectly withprocessor 232 b and Domain B database 240 b. Similarly, it is throughcommunication subsystems 238 b and 238 a and interface 264, thatprocessor 232 b is communicatively connected to and interacts directlyor indirectly with processor 232 a and Domain A database 240 a.

Communication subsystem 238 a is communicatively connected to andinteracts directly or indirectly with communication subsystem 258 a (ofDomain A Network Element 250 a) using interface 262 a. Accordingly, itis through communication subsystems 238 a and 258 a and interface 262 a,that processor 252 a is communicatively connected to and interactsdirectly or indirectly with processor 232 a and Domain A database 240 a.

Communication subsystem 238 b is communicatively connected to andinteracts directly or indirectly with communication subsystem 258 b (ofDomain B Network Element 250 b) using interface 262 b. Accordingly, itis through communication subsystems 238 b and 258 b and interface 262 b,that processor 252 b is communicatively connected to and interactsdirectly or indirectly with processor 232 b and Domain B database 240 b.

Communication subsystem 258 a is communicatively connected to andinteracts directly or indirectly with communication subsystem 258 busing interface 266.

Accordingly, it is through communication subsystems 258 a and 258 b andinterface 266, that processor 252 a is communicatively connected to andinteracts directly or indirectly with processor 252 b.

In example embodiments, processors 132, 152 and 172 of FIG. 1 andprocessors 212, 232 a, 232 b, 252 a and 252 b of FIG. 2, each includehardware or software or any combination of hardware or software.

In example embodiments, memories 134, 154 and 174 of FIG. 1 and memories214, 234 a, 234 b, 254 a and 254 b of FIG. 2 are each persistent stores,such as for example flash memory, read-only (ROM) memory or othersimilar storage.

In example embodiments, Domain A database 140 of FIG. 1, and Networkdatabase 220, Domain A database 240 a and Domain B database 240 b ofFIG. 2, can be of any type and can be different types from each other.For a given SON function manager software application, its database canstore the following information for each SON function that is alsostored in the SON function manager software application: an input impacttime, an input scope, information elements of the input scope, anobjective, an output impact time, an impact area, and informationelements of the impact area. The database may also store suchinformation for other SON functions that are not stored in the SONfunction manager software application. The database may also storenetwork-specific or domain-specific topology and/or network elementinformation. It should be appreciated that the content in the databasedepends on implementation details and configuration of a correspondingnetwork or domain SON function manager. Further, it should beappreciated that it bears no significance where the database, or part ofthe database, is located, and whether or not some databases, areintegrated together.

In example embodiments, interfaces 110 and 120 of FIG.1 are domainspecific management interfaces (such as for example itf-S interfaces),and interfaces 260 a, 260 b, 262 a and 262 b of FIG. 2, are networkmanagement interfaces (such as for example Itf-N interfaces). In anotherexample embodiment, interfaces 110 and 120 are also network managementinterfaces. In example embodiments, interface 190 of FIG. 1 andinterfaces 264 and 266 of FIG. 2 are peer-to-peer interfaces, such asfor example: inter-base station interfaces (such for example X2interfaces) and inter-domain manager interfaces (such as for exampleItf-P2P interfaces). In example embodiments, any of the interfaces 110,120, 260 a, 260 b, 262 a, 262 b, 190, 264 and 266 can be defined by anetwork operator, or by vendors of the SON function managers and networkelements, or can be a standardized interface.

FIGS. 1 and 2 illustrate communication systems 100 and 200 having asimplified architecture and therefore only some elements and functionsare shown. The illustrated elements and functions are all logical units,whose implementation may differ from what is shown in FIGS. 1 and 2. Theconnections shown in FIGS. 1 and 2 are logical connections; the actualphysical connections may be different. It is apparent to a personskilled in the art that the systems also include other elements andfunctions, including other SON functions that are not illustrated ordiscussed in this Detailed Description.

It bears no significance in example embodiments how SON functions areallocated (i.e. distributed, centralized and hybrid/multi-layer mannerallocations may be used). Furthermore, example embodiments areimplementable regardless of where the SON functions are implemented (forexample at network element level, at domain SON function manager level,and/or at network SON function manager level).

FIGS. 3-7 illustrate methods 300-700 to prevent a potential conflictamong a first instance of a first SON function, and a second instance ofa second SON function. As disclosed throughout this DetailedDescription, a potential conflict can be defined as a scenario in whichat least one information element output by a first instance would makeat least a substantial impact on at least one information elementcollected, decision making and/or at least one information elementoutput by a second instance. Examples of such substantial impact are:the first instance affecting the originally intended operation of thesecond instance and lowering the corresponding performance of the secondinstance; the first instance distorting the input to the secondinstance, the first instance blocking the execution of the secondinstance, the first instance canceling the intended action of the secondinstance, the first instance canceling the change made by the secondinstance, the first instance deleting or diminishing the performancegain achievable by the second instance, the first instance competingwith the second instance to solve the problem that could be solved bythe second instance alone. Furthermore, a potential conflict isdirectional from one instance to another. In other words, when a firstinstance conflicts with a second instance in a particular way, this doesnot mean that the second instance conflicts with the first instance inthe same way.

The methods 300-700 can be implemented by any of processors 132, 152 and172 of FIG. 1 and processors 212, 232 a, 232 b, 252 a and 252 b of FIG.2. In an example embodiment, any of the methods 300-700 is executed inresponse to receiving a request to execute the first instance or arequest to output at least one information element by the firstinstance. The request may originate and be sent in a communication fromany of processors 132, 152 and 172 of FIG. 1 and processors 212, 232 a,232 b, 252 a and 252 b of FIG. 2, that is communicatively connected tothe processor executing the method. For example, if processor 132 (ofFIG. 1) were executing method 300, it would do so in response toreceiving a request to execute the first instance or request to outputat least one information element by the first instance, received fromanother processor communicatively connected to processor 132. Examplesof such a request are: “power up”, “cell a1, tilt-up delta 2 degrees”,“change transmission power by x amount”, and “increase 20% of cell a2'scoverage towards failed cell a3”.

FIG. 3 illustrates a method 300 to prevent a potential conflict among afirst instance of a first SON function, and a second instance of asecond SON function.

At 310, an input impact time, an input scope and an objective of a firstinstance of a first SON function are obtained. As disclosed throughoutthis Detailed Description: an instance of a SON function (also referredto throughout this Detailed Description as a SON function instance, afirst instance, or a second instance) can be defined as a run-timeprocess that instantiates a SON function in a network environment; aninput impact time can be defined as the time period that at least oneinformation element input to a SON function instance would be impacted,by at least one information element that is output by another SONfunction instance; an input scope can be defined as at least oneinformation element that a SON function instance collects in order toexecute; an information element can be defined as a piece of data; andan objective of a SON function instance can be defined as a goal of theSON function instance. In an example embodiment, an information elementis a piece of data about one of: a network element or multiple networkelements (such as for example a user equipment (UE), a cell, a cellpair, cell neighbors, a cell cluster), a sub-network or even the entirenetwork. Example information elements are pieces of data about: a UE'sbehavior, a cell's characteristics, a home subscriber server (HSS)/homelocation register (HLR) entry, and an operations support system (OSS)record. Example objectives of SON function instances are: increasecapacity of a cell and minimize handovers of signals from one cell toanother.

In an example embodiment, any one of the input impact time, the inputscope and the objective of the first instance of the first SON functionmay be obtained by the processor executing method 300, from a databasecommunicatively connected to that processor. For example, if processor132 (of FIG. 1) were executing method 300, and Domain A database 140 (ofFIG. 1) stored the input impact time, the input scope and the objectiveof the first instance, processor 132 could obtain these items fromdatabase 140 because it is communicatively connected to it. In anotherexample, if processor 152 (of Domain A) were executing method 300, andDomain A database 140 stored the input impact time, the input scope andthe objective of the first instance, processor 152 could obtain theseitems from database 140, because it is communicatively connected to it.

In another example embodiment, any one of the input impact time, theinput scope and the objective of the first instance may be sent to theprocessor that is executing method 300, from another processorcommunicatively connected to that processor. Any one of the input impacttime, the input scope and the objective, may be sent to the processorthat is executing method 300, from another processor, in a request toexecute the first instance or a request to output at least oneinformation element by the first instance.

320 is next. At 320, an input impact time, an input scope and anobjective of an instance of a second SON function are obtained.

In an example embodiment, the input impact time, the input scope and theobjective of the second instance may be obtained by the processor, froma database communicatively connected to that processor. For example, ifprocessor 232 a (of FIG. 2) were executing method 300, and Networkdatabase 220 (of FIG. 2) stored the input impact time, the input scopeand the objective of the second instance, processor 232 a could obtainthese items from Network database 220 because it is communicativelyconnected to database 220 through communications subsystems 238 a and218 and interface 260 a. An example scenario in which a network database(such as network database 220) would store the input impact time, theinput scope and the objective of the second instance, is when the secondSON function resides in a different domain that the first SON function,and a database within the domain of the first instance does not storeinformation about the second instance.

330 is next. At 330, whether there is an overlap among the input impacttime of the first instance and the input impact time of the secondinstance, is determined. If there is an overlap, 340 is next. If thereis not an overlap, 370 is next.

At 340, whether there is an overlap among the input scope of the firstinstance and the input scope of the second instance, is determined. Ifthere is an overlap, 350 is next. If there is not an overlap, 370 isnext.

At 350, whether the objective of the first instance and the objective ofthe second instance are the same or substantially the same, isdetermined. If they are the same or substantially the same, 380 is next.If they are not the same or substantially the same, 360 is next.

At 360, whether the objective of the first instance contradicts orsubstantially contradicts with the objective of the second instance, isdetermined. If the objectives contradict or substantially contradicteach other, 380 is next. If the objectives do not contradict orsubstantially contradict each other, 370 is next.

At 370, it is determined that a potential conflict does not exist.

At 380, it is determined that a potential conflict exists, and aresolution to prevent the potential conflict is initiated.

FIG. 4 illustrates another method 400 to prevent a potential conflictamong a first instance of a first SON function, and a second instance ofa second SON function.

At 410, an output impact time and an impact area of a first instance ofa first SON function is obtained.

As disclosed throughout this Detailed Description, an output impact timecan be defined as the time period that at least one information elementoutput by a SON function instance would impact: at least one informationelement input to another SON function instance or at least oneinformation element output by the other SON function instance.

Furthermore, as disclosed throughout this Detailed Description, animpact area can be defined as at least one information element output bya SON function instance and any other information element(s) affected bythe information element(s) output by the SON function instance. Anexample of how an information element output by a SON function instancecould affect other information elements is as follows. A SON functioninstance changes the power parameter of cell 1 and this results in acoverage change of cell 1. The resulted coverage change of cell 1affects information elements of cell 2, a neighbor of cell 1. In thisexample, both the power parameter of cell 1 and the affected informationelements of cell 2 make up the impact area.

In an example embodiment, any one of the output impact time and impactarea of the first instance may be obtained by the processor executingmethod 400, from a database communicatively connected to that processor.

In another example embodiment, any one of the output impact time and theimpact area of the first instance may be sent to the processor that isexecuting method 400, from another processor communicatively connectedto that processor. In an example embodiment, any one of the outputimpact time and the impact area, may be received by the processor thatis executing method 400, from another processor that is requesting toexecute the first instance or requesting to output at least oneinformation element by the first instance.

420 is next. At 420, an input impact time and an input scope of a secondinstance of a second SON function is obtained. In an example embodiment,the input impact time and the input scope may be obtained by theprocessor executing method 400, from a database communicativelyconnected to that processor.

430 is next. At 430, whether there is an overlap among the output impacttime of the first instance and the input impact time of the secondinstance, is determined. If there is an overlap, 440 is next. If thereis not an overlap, 460 is next.

At 440, whether there is an overlap among at least one informationelement in the impact area of the first instance and in the input scopeof the second instance, is determined. If there is an overlap, 450 isnext. If there is not an overlap, 460 is next.

At 450, whether at least one of the information elements in the impactarea of the first instance would substantially change at least one ofthe information elements in the input scope of the second instance, isdetermined. If at least one of the information elements in the inputscope would be substantially changed, 470 is next. If none of theinformation elements in the input scope would be substantially changed,460 is next.

At 460, it is determined that a potential conflict does not exist.

At 470, it is determined that a potential conflict exists, and aresolution to prevent the potential conflict is initiated.

FIG. 5 illustrates yet another method 500 to prevent a potentialconflict among a first instance of a first SON function, and a secondinstance of a second SON function. (Method 400 included a determinationof whether the first instance conflicts with the second instance in aparticular way. Method 500 includes a determination of whether thesecond instance conflicts with the first instance in the same particularway.)

At 510, an input impact time and an input scope of a first instance of afirst SON function are obtained. In an example embodiment, any one ofthe input impact time and the input scope may be obtained by theprocessor executing method 500, from a database communicativelyconnected to that processor.

In another example embodiment, any one of the input impact time and aninput scope of the first instance may be sent to the processor that isexecuting method 500, from another processor communicatively connectedto that processor. Any one of the input impact time and the input scope,may be sent to the processor that is executing method 300, from anotherprocessor that is requesting to execute the first instance or requestingto output at least one information element by the first instance.

520 is next. At 520, an output impact time and an impact area of asecond instance of a second SON function are obtained. In an exampleembodiment, the output impact time and an impact area of the secondinstance may be obtained by the processor executing method 500, from adatabase communicatively connected to that processor.

530 is next. At 530, whether there is an overlap among the output impacttime of the second instance and the input impact time of the firstinstance, is determined. If there is an overlap, 540 is next. If thereis not an overlap, 560 is next.

At 540, whether there is an overlap among at least one informationelement in the impact area of the second instance and in the input scopeof the first instance, is determined. If there is an overlap, 550 isnext. If there is not an overlap, 560 is next.

At 550, whether at least one of the information elements in the impactarea of the second instance would substantially change at least one ofthe information elements in the input scope of the first instance, isdetermined. If at least one of the information elements in the inputscope would be substantially changed, 570 is next. If none of theinformation elements in the input scope would be substantially changed,560 is next.

At 560, it is determined that a potential conflict does not exist.

At 570, it is determined that a potential conflict exists, and aresolution to prevent the potential conflict is initiated.

FIG. 6 illustrates another method 600 to prevent a potential conflictamong a first instance of a first SON function, and a second instance ofa second SON function.

At 610, an output impact time and an impact area of a first instance ofa first SON function is obtained. In an example embodiment, any one ofthe output impact time and the impact area may be obtained by theprocessor executing method 600, from a database communicativelyconnected to that processor.

In another example embodiment, any one of the output impact time and theimpact area may be sent to the processor that is executing method 600,from another processor communicatively connected to that processor. Anyone of the output impact time and the impact area, may be sent to theprocessor that is executing method 600, from another processor that isrequesting to execute the first instance or requesting to output atleast one information element by the first instance.

620 is next. At 620, an output impact time and an impact area of asecond instance of a second SON function is obtained. In an exampleembodiment, the output impact time and the impact area may be obtainedby the processor executing method 600, from a database communicativelyconnected to that processor.

630 is next. At 630, whether there is an overlap among the output impacttime of the first instance and the output impact time of the secondinstance, is determined. If there is an overlap, 640 is next. If thereis not an overlap, 660 is next.

At 640, whether there is an overlap among at least one informationelement in the impact area of the first instance and in the impact areaof the second instance, is determined. If there is an overlap, 650 isnext. If there is not an overlap, 660 is next.

At 650, whether at least one of the information elements in the impactarea of the first instance would substantially change at least one ofthe information elements in the in the impact area of the secondinstance, is determined. If at least one of the information elements inthe impact area of the second instance would be substantially changed,670 is next. If none of the information elements in the impact area ofthe second instance would be substantially changed, 660 is next.

At 660, it is determined that a potential conflict does not exist.

At 670, it is determined that a potential conflict exists, and aresolution to prevent the potential conflict is initiated.

FIG. 7 illustrates yet another method 700 to prevent a potentialconflict among a first instance of a first SON function, and a secondinstance of a second SON function. (Method 600 included a determinationof whether the first instance conflicts with the second instance in aparticular way. Method 700 includes a determination of whether thesecond instance conflicts with the first instance in the same particularway.)

At 710, an output impact time and an impact area of a first instance ofa first SON function is obtained. In an example embodiment, any one ofthe output impact time and the impact area may be obtained by theprocessor executing method 700, from a database communicativelyconnected to that processor.

In another example embodiment, any one of the output impact time and theimpact area may be sent to the processor that is executing method 700,from another processor communicatively connected to that processor. Anyone of the output impact time and the impact area, may be sent to theprocessor that is executing method 700, from another processor that isrequesting to execute the first instance and requesting to output atleast one information element by the first instance.

720 is next. At 720, an output impact time and an impact area of asecond instance of a second SON function is obtained. In an exampleembodiment, the output impact time and the impact area may be obtainedby the processor executing method 700, from a database communicativelyconnected to that processor.

730 is next. At 730, whether there is an overlap among the output impacttime of the first instance and the output impact time of the secondinstance, is determined. If there is an overlap, 740 is next. If thereis not an overlap, 760 is next.

At 740, whether there is an overlap among at least one informationelement in the impact area of the first instance and in the impact areaof the second instance, is determined. If there is an overlap, 750 isnext. If there is not an overlap, 760 is next.

At 750, whether at least one of the information elements in the impactarea of the second instance would substantially change at least one ofthe information elements in the impact area of the first instance, isdetermined. If at least one of the information next. If none of theinformation elements in the impact area of the first instance would besubstantially changed, 760 is next.

At 760, it is determined that a potential conflict does not exist.

At 770, it is determined that a potential conflict exists, and aresolution to prevent the potential conflict is initiated.

In the methods 300-700 discussed above, particularly at 380, 470, 570,670 and 770, example resolutions to prevent the potential conflict are:to not execute the first instance; to reject a request to output atleast one information element by the SON function instance that isrequesting to output the at least one information element; to executethe one of the first and second instances, that has a predeterminedhigher priority; to approve of a request to output at least oneinformation element by one of the first and second instances, that has apredetermined higher priority; if the second instance is currentlyexecuting, to not execute the first instance; and if the second instanceis currently executing, to reject a request to output at least oneinformation element by the first instance.

In example embodiments, all of methods 300-700 are executed to determineand prevent any potential conflicts among the first and secondinstances. In another example embodiment, if after executing one ofmethods 300-700, it determined that a potential conflict exists, aresolution to prevent the potential conflict is initiated and theremaining of the methods 300-700 are not executed.

The blocks of methods 300-700 in FIGS. 3-7 are in no absolutechronological order, and some of the blocks may be performedsimultaneously or in an order differing from the given one. Some of theblocks or part of the blocks can also be left out or replaced by acorresponding block or part of the blocks.

The terms “request” or “requesting”, disclosed throughout the DetailedDescription does not imply that a server-client or a master-slaveapproach is or needs to be used. The terms “requesting” and “request”can be defined as asking and the act of asking. Furthermore, therequests disclosed throughout the Detailed Description are only examplesand may even include several separate communications for sending thesame information. In addition, the requests may also contain otherinformation.

It will be obvious to a person skilled in the art that, as technologyadvances, the inventive concept can be implemented in various ways. Theinvention and its embodiments are not limited to the examples describedabove but may vary within the scope of the claims.

1. A processor implemented method to prevent a potential conflict amonga first instance of a first self-organizing network (“SON”) function,and a second instance of a second SON function, comprising: obtaining afirst input impact time, a first input scope and a first objective ofthe first instance, and obtaining a second input impact time, a secondinput scope and a second objective of the second instance. determiningif there is a first overlap among the first input impact time and thesecond input impact time; if there is the first overlap, determining ifthere is a second overlap among the first input scope and the secondinput scope; if there is the second overlap, determining if the firstobjective and the second objective are the same or substantially thesame and if so, determining that the potential conflict exists; if thereis the second overlap, determining if the first objective contradicts orsubstantially contradicts with the second objective and if so,determining that the potential conflict exists; and if the potentialconflict exists, initiating a resolution to prevent the potentialconflict.
 2. The method of claim 1, wherein the method is executed, inresponse to the processor receiving a request to execute the firstinstance or a request to output at least one information element by thefirst instance.
 3. The method of claim 1, wherein the resolution toprevent the potential conflict is to not execute the first instance orto reject a request to output at least one information element by thefirst instance.
 4. The method of claim 1, wherein the resolution toprevent the potential conflict is to not execute the first instance orto reject a request to output at least one information element by thefirst instance, if the second instance is currently executing.
 5. Themethod of claim 1, wherein the resolution to prevent the potentialconflict is to execute one of the first and second instances or toapprove a request to output at least one information element by one ofthe first and second instances, that has a predetermined higherpriority.
 6. A computing device to prevent a potential conflict among afirst instance of a SON function, and a second instance of a second SONfunction, comprising: a processor configured to: obtain a first inputimpact time, a first input scope and a first objective of the firstinstance; obtain a second input impact time, a second input scope and asecond objective of the second instance; determine if there is a firstoverlap among the first input impact time and the second input impacttime; if there is the first overlap, determine if there is a secondoverlap among the first input scope and the second input scope; if thereis the second overlap, determine if the first objective and the secondobjective are the same or substantially the same and if so, determinethat the potential conflict exists; if there is the second overlap,determine if the first objective contradicts or substantiallycontradicts with the second objective and if so, determine that thepotential conflict exists; and if the potential conflict exists,initiate a resolution to prevent the potential conflict.
 7. Thecomputing device of claim 6, wherein the processor is further configuredto prevent the potential conflict, in response to receiving a request toexecute the first instance or a request to output at least oneinformation element by the first instance.
 8. The computing device ofclaim 6, wherein the resolution to prevent the potential conflict is tonot execute the first instance or to reject a request to output at leastone information element by the first instance.
 9. The computing deviceof claim 6, wherein the resolution to prevent the potential conflict isto not execute the first instance or to reject a request to output atleast one information element by the first instance, if the secondinstance is currently executing.
 10. The computing device of claim 6,wherein the resolution to prevent the potential conflict is to executeone of the first and second instances or to approve a request to outputat least one information element by one of the first and secondinstances, that has a predetermined higher priority.
 11. A processorimplemented method to prevent a potential conflict among a firstinstance of a first SON function, and a second instance of a second SONfunction, comprising: obtaining an output impact time and an impact areaof the first instance, and obtaining an input impact time and an inputscope of the second instance. determining if there is a first overlapamong the output impact time and the input impact time; and if there isthe first overlap, determining if there is a second overlap among atleast one of information element in the impact area and in the inputscope; if there is the second overlap, determining if at least one ofthe information element in the impact area would substantially change atleast one of the information elements in the input scope, and if so,determining that the potential conflict exists; and if the potentialconflict exists, initiating a resolution to prevent the potentialconflict.
 12. The method of claim 11, wherein the method is executed, inresponse to the processor receiving a request to execute the firstinstance or a request to output at least one of the information elementsby the first instance.
 13. The method of claim 11, wherein theresolution to prevent the potential conflict is to not execute the firstinstance or to reject a request to output at least one of theinformation elements by the first instance.
 14. The method of claim 11,wherein the resolution to prevent the potential conflict is to notexecute the first instance or to reject a request to output at least oneof the information elements by the first instance, if the secondinstance is currently executing.
 15. The method of claim 11, wherein theresolution to prevent the potential conflict is to execute one of thefirst and second instances or to approve a request to output at leastone of the information elements by one of the first and secondinstances, that has a predetermined higher priority.
 16. A computingdevice to prevent a potential conflict among a first instance of a firstSON function, and a second instance of a second SON function,comprising: a processor configured to: obtain an output impact time andan impact area of the first instance, and obtaining an input impact timeand an input scope of the second instance. determine if there is a firstoverlap among the output impact time and the input impact time; and ifthere is the first overlap, determine if there is a second overlap amongat least one of information element in the impact area and in the inputscope; if there is the second overlap, determine if at least one of theinformation element in the impact area would substantially change atleast one of the information elements in the input scope, and if so,determine that the potential conflict exists; and if the potentialconflict exists, initiate a resolution to prevent the potentialconflict.
 17. The computing device of claim 16, wherein the processor isfurther configured to prevent the potential conflict, in response toreceiving a request to execute the first instance or a request to outputat least one of the information elements by the first instance.
 18. Thecomputing device of claim 16, wherein the resolution to prevent thepotential conflict is to not execute the first instance or to reject arequest to output at least one of the information elements by the firstinstance.
 19. The computing device of claim 16, wherein the resolutionto prevent the potential conflict is to not execute the first instanceor to reject a request to output at least one of the informationelements by the first instance, if the second instance is currentlyexecuting.
 20. The computing device of claim 16, wherein the resolutionto prevent the potential conflict is to execute one of the first andsecond instances or to approve of a request to output at least one ofthe information elements by one of the first and second instances, thathas a predetermined higher priority.